0.0
NA
CVE-2026-0798
Gitea Release Email Notifications Leak Private Repository Release Details After Access Revocation
Description

Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content.

INFO

Published Date :

Jan. 22, 2026, 10:16 p.m.

Last Modified :

Jan. 22, 2026, 10:16 p.m.

Remotely Exploit :

No

Source :

88ee5874-cf24-4952-aea0-31affedb7ff2
Affected Products

The following products are affected by CVE-2026-0798 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Revoke email notifications for users accessing private repositories after access is removed.
  • Ensure Gitea correctly revokes email notifications for private repositories.
  • Verify user access permissions are consistently enforced.
  • Test notification system after repository privacy changes.
  • Implement stricter access control logic for notifications.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-0798.

URL Resource
https://blog.gitea.com/release-of-1.25.4/
https://github.com/go-gitea/gitea/pull/36319
https://github.com/go-gitea/gitea/releases/tag/v1.25.4
https://github.com/go-gitea/gitea/security/advisories/GHSA-f4wq-6ww5-m56p
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-0798 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-0798 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-0798 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 88ee5874-cf24-4952-aea0-31affedb7ff2

    Jan. 22, 2026

    Action Type Old Value New Value
    Added Description Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content.
    Added CWE CWE-284
    Added Reference https://blog.gitea.com/release-of-1.25.4/
    Added Reference https://github.com/go-gitea/gitea/pull/36319
    Added Reference https://github.com/go-gitea/gitea/releases/tag/v1.25.4
    Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-f4wq-6ww5-m56p
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.